Methods and apparatus to monitor, verify, and rate the performance of airings of commercials

ABSTRACT

Methods and apparatus to monitor, verify, and rate the performance of airings of commercials are disclosed. An example method includes analyzing received advertisement detection information associated with the advertisement, the advertisement detection information detected from a presentation of the advertisement; identifying a buy order corresponding to the presentation of the advertisement based on the advertisement detection information; determining a purchased ratings value from the buy order; comparing the purchased ratings value of the buy order to received ratings information corresponding to the presentation of the advertisement to determine whether the advertisement was presented as indicated in the buy order; and generating a performance monitoring report using the buy order and the advertisement detection information to indicate whether the ratings information is less than the purchased ratings value.

RELATED APPLICATIONS

This patent arises from a continuation of U.S. patent application Ser. No. 14/144,189 filed Dec. 30, 2013, now U.S. Pat. No. 9,064,270 issued on Jun. 23, 2015, which is a continuation of U.S. patent application Ser. No. 12/350,223, filed Jan. 7, 2009, now U.S. Pat. No. 8,701,136, which claims priority from U.S. Provisional Patent Application No. 61/019,501, filed Jan. 7, 2008, entitled “METHODS AND APPARATUS TO MONITOR, VERIFY, AND RATE THE PERFORMANCE OF AIRINGS OF COMMERCIALS.” U.S. patent application Ser. No. 14/144,189, U.S. patent application Ser. No. 12/350,223, and U.S. Provisional Patent Application Ser. No. 61/019,501 are hereby incorporated by reference in their entireties.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to media monitoring and, more particularly, to methods and apparatus to monitor, verify, and rate the performance of airings of commercials.

BACKGROUND

When advertisers purchase advertising exposure (e.g., a commercial campaign on a television network), a contract is negotiated that identifies details and/or benchmarks for how the advertisement is to be presented. For example, the contract may specify the time of day during which an advertisement is to be presented, the type of programming (e.g., television program) during which an advertisement is to be presented, the type of programming with which an advertisement is not to be presented, how much time is expected to pass between advertisement presentations, etc. Advertisement handlers (e.g., a television network) must then manage the presentation of advertisements to meet the requirements defined by the contract.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example performance verifier apparatus to generate commercial performance verification reports based on commercial detection information, program schedule information, and commercial buy information.

FIG. 2 illustrates an example performance monitoring report generator apparatus to generate performance monitoring reports based on information from the example performance verification apparatus of FIG. 1, ratings data, and user guideline information.

FIG. 3 is a flow diagram representative of machine readable instructions that may be executed to implement the performance monitoring report generator apparatus of FIG. 2.

FIG. 4 is a user login user interface screen to authenticate registered users and grant those users access to the example performance monitoring report generator apparatus of FIG. 2.

FIG. 5 is a search user interface screen to enable users to request reports from the example performance monitoring report generator apparatus of FIG. 2.

FIG. 6 is a system administrator user interface screen to enable administrator-level users to create advertising agency accounts.

FIG. 7 is a user records user interface screen to display registered users associated with different advertisement agencies.

FIG. 8 is an advertiser/product records user interface screen to show advertiser and product information for different advertisement agencies.

FIG. 9 is an advertisement campaign user interface screen to list advertising campaigns from different advertisers.

FIG. 10 is an entry/edit user interface screen to enable a user to enter estimated information related to commercial airings of an advertisement campaign.

FIG. 11 is a ratings methodology user interface screen to enable a user to specify a particular ratings methodology to use for rating a particular advertisement campaign.

FIG. 12 is an implementation guidelines user interface screen to enable a user to specify rules for how commercials are to be broadcast.

FIG. 13 is an add/edit traffic user interface screen to enable a user to add or edit commercials for different advertisement campaigns.

FIG. 14 is a multi-market view total user interface screen to enable a user to view total advertisement campaign performance information.

FIG. 15A is a first part of a multi-market view daypart user interface screen to enable a user to view daypart advertisement campaign performance information.

FIG. 15B is a second part of a multi-market view daypart user interface screen to enable a user to view daypart advertisement campaign performance information.

FIG. 16A is a first part of a multi-market view weekly user interface screen to enable a user to view weekly advertisement campaign performance information.

FIG. 16B is a second part of a multi-market view weekly user interface screen to enable a user to view weekly advertisement campaign performance information.

FIG. 17 is a single-market performance user interface screen to display performance information of a single estimate in a single market.

FIG. 18 is a single-market weekly performance user interface screen to display performance information of a single estimate in a single market by week.

FIG. 19 is a station view total user interface screen to display total estimated versus actual rating and gross rating point (GRP) data for a particular station.

FIG. 20 is a station view weekly user interface screen to display estimated versus actual rating and GRP data for a particular station by week.

FIG. 21A is a first part of a station view spot detail user interface screen to display detailed information about detected and bought spots for a particular station.

FIG. 21B is a second part of a station view spot detail user interface screen to display detailed information about detected and bought spots for a particular station.

FIG. 22 is a flash report user interface to enable a user to select rows of data from different reports and send the data to a recipient party.

FIG. 23 is a guidelines violation report default user interface screen to display an overview of violation information associated with aired commercials.

FIG. 24A is a first part of a station violation detail user interface screen to display detailed violation information associated with aired commercials.

FIG. 24B is a second part of a station violation detail user interface screen to display detailed violation information associated with aired commercials.

FIG. 25A is a first part of an implementation guidelines user interface screen to allow a user to configure the detection of violations of the guidelines specified in a buy.

FIG. 25B is a second part of an implementation guidelines user interface screen to allow a user to configure the detection of violations of the guidelines specified in a buy.

FIG. 26 is an example multi-market view user interface screen that includes an audit index.

FIG. 27 is a violations report user interface screen that displays detailed information about guideline violations.

FIG. 28 is a block diagram of an example processor system that may be used to implement some or all of the example methods and apparatus described herein.

FIG. 29 is an implementation of report user interface for displaying information related to maximum exposure for aired commercials.

FIG. 30 is an implementation of report user interface for displaying information related to maximum exposure for aired commercials.

FIG. 31 is an implementation of report user interface for displaying information related to maximum exposure for aired commercials.

FIG. 32 is an implementation of report user interface for displaying information related to maximum exposure for aired commercials.

FIGS. 15A and 15B represent a single figure and are referenced as FIG. 15 throughout the specification. FIGS. 16A and 16B represent a single figure and are referenced as FIG. 16 throughout the specification. FIGS. 21A and 21B represent a single figure and are referenced as FIG. 21 throughout the specification. FIGS. 24A and 24B represent a single figure and are referenced as FIG. 16 throughout the specification. FIGS. 25A and 25B represent a single figure and are referenced as FIG. 25 throughout the specification.

DETAILED DESCRIPTION

Although the following discloses example apparatus and systems including, among other components, software executed on hardware, it should be noted that such apparatus and systems are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these hardware and software components could be embodied exclusively in hardware, exclusively in software, or in any combination of hardware and software. Accordingly, while the following describes example methods, apparatus, and systems, persons having ordinary skill in the art will readily appreciate that the examples provided are not the only way to implement such methods, apparatus, and systems.

In general, the example methods and apparatus described herein may be used to monitor, verify, and rate the performance of airings of commercials. Although the example methods and apparatus are described herein using television commercials, the example methods and apparatus may be used in connection with commercials presented via different mediums including, for example, radio. As described below, the example methods and apparatus described herein are configured to generate, organize and present performance information related to the monitoring, verification and rating of aired commercials. The performance information is generated based on user-provided information that specifies how advertisement campaigns are expected to perform. In addition, the example methods and apparatus described herein enable users to specify how commercials are to be monitored and analyzed. The performance information is organized and presented using different user interface screens that enable users to specify different criteria associated with how the performance information is presented. The example implementation described herein enables advertising handlers to monitor advertising presentation while a campaign is in progress to enable adjustments to be made to the campaign to meet the specifications of the advertiser.

To verify the airing of commercial advertisements, the example methods and apparatus described herein receive user-provided estimate information describing purchase order or buy specifics for each commercial. The purchase order or buy specifics are then used to determine whether the commercials were aired as ordered and whether they reached a target demographic audience. In some example implementations, the example methods and apparatus described herein are implemented in connection with example systems, methods and apparatus described in U.S. provisional patent application No. 60/976,692, filed on Oct. 1, 2007, and titled “Systems and Methods to Associate Related Market Broadcast Detections into National Detections,” U.S. patent application Ser. No. 12/242,192, filed on September 2008, and titled “Systems, Apparatus and Method to Associate Related Market Broadcast Detections with a Multi-Market Media Broadcast,” and U.S. Pat. No. 7,039,931, issued on May 2, 2006, and titled “Multi-Market Broadcast Tracking, Management and Reporting Method and System,” all of which are hereby incorporated by reference herein in their entireties.

In the illustrated examples described herein, commercial advertisements can be bought on a per spot or per national basis. A spot refers to the broadcast source for the television (TV) programming being discussed. A spot commercial is a commercial run on a local broadcaster, such as WABC. A spot rating is the rating for that local broadcaster. A national refers to a commercial run in connection with TV programming from a national TV broadcast network (e.g., ABC, CBS) or national cable network (e.g., Life, USA, Sci-Fi, etc.). The commercial (e.g., spots or nationals) can be bought by advertisers or advertising agencies. An advertiser is a product manufacturer or service provider that is the source of goods or services being advertised. Example advertisers are car manufacturers, food manufacturers, internet service providers, entertainment service providers, etc. An advertising agency is an agency that may be hired by an advertiser to create and/or manage advertisements including the purchasing of advertisement spots or nationals to air the advertiser's advertisements.

When an advertiser or advertising agency purchases a spot or a national, it is referred to as a buy (e.g., a purchase order). A buy is an instruction from an advertiser (or advertising agency) to a broadcaster to run a commercial or set of commercials over a set time or series of times with set rules (i.e., guidelines for airing commercials). Buy information (or purchase order information) includes estimate information to estimate airing specifics of a particular advertisement including, for example, goals for reach, frequency, demographics, average rating and market, among other metrics. The example methods and apparatus described herein are configured to generate reports indicating whether commercial airing guidelines (as set forth by rules of the buy information) have been met or violated for corresponding commercial airings.

The terms estimate and campaign are used interchangeably to refer to a subcomponent (e.g., reach, frequency, demographics, average rating, market, etc.) of the estimate of a media plan. A buy is the implementation instruction of an estimate (or campaign). The term traffic refers to instructions specifying what commercials may be aired when fulfilling a buy for a campaign. When a commercial is permitted to be run as part of a campaign, it is said to be trafficked to that campaign. When monitoring airings of commercials, a match occurs for each detection of an encoded commercial that has been matched to a buy (and, thus, to a campaign). A detected commercial that does not match any buys (and, thus, does not match any campaigns) is referred to as unordered. An allowance refers to a window of time around the buy instructions during which a commercial may be aired and still be matched to a buy.

Turning to FIG. 1, an illustrated example performance verifier apparatus 100 may be used to generate commercial performance verification reports 102 based on commercial detection information 104 (collected program name code, electronic signature, or diary information), program schedule information 106, and commercial buy information 110. The example performance verifier apparatus 100 is an analytic system that receives the commercial detection information 104, the program schedule information 106, and the commercial buy information 110 to generate the performance verification reports 102. The commercial performance verification reports 102 describe how a user (e.g., an advertising agency or an advertiser) expected a commercial to perform and the actual performance that was detected based on the airing(s) of that commercial.

FIG. 2 illustrates an example performance monitoring report generator apparatus 200 to generate performance monitoring reports 202 based on information from the example performance verification apparatus 100 of FIG. 1, ratings data 204, and user guideline information 206. The performance monitoring reports 202 are used to report whether commercials are running when ordered, whether the commercials are run during time periods getting sufficiently high ratings, and whether the airings of the commercials are within constraints or limits specified by an advertiser or advertising agency. Each of the performance monitoring reports 202 can include one or more of ratings report information 208, verification report information 210, and guidelines report information 212. While the performance verifier apparatus 100 of FIG. 1 verifies whether commercials ran when ordered based on buys (e.g., a particular commercial ran in 5 spots during the week of March 15), the performance monitoring report generator apparatus 200 informs users whether their buy contracts are being correctly fulfilled by verifying whether commercials ran when ordered based on buys (e.g., the buy information 110), based on whether the commercials were received by the expected audience (e.g., a demographic group of males between the ages of 18-54, and a 3.6 average rating), and based on whether the commercials were run as instructed (e.g., five spots per week during the week of March 15, but never during the Jerry Springer show).

In the illustrated examples described herein, performance monitoring report generator apparatus 200 presents performance-related data using a series of user interface screens described below that are arranged in a drill-down hierarchy ranging from high level summary data to specific instance datum. This drill-down hierarchy organization allows users to relatively quickly identify under-performing buys and relatively quickly isolate the cause of the underperformance. The performance monitoring report generator apparatus 200 implements a color-coded index (e.g., a red index) to highlight data indicative of under-performance, which allows users to identify performance thresholds against which different data (e.g., rows of a data grid) is compared.

In the illustrated examples described herein, the performance monitoring report generator apparatus 200 primarily presents performance-related information using data grids. At each level of the drill-down hierarchy, the performance monitoring report generator apparatus 200 presents different data grids based on different combinations of variables/data. The processes implemented using the performance monitoring report generator apparatus 200 support the various ways that users think about data off-line or think about the concept of measuring or quantifying performance.

To enhance communications and foster collaborative work environments, the performance monitoring report generator apparatus 200 enables users to select particular data from reports (e.g., using the flash report user interface described in connection with FIG. 22) and send the selected data to others via, for example, email. Alternatively or additionally, users may download reports into spreadsheet or PDF formats, which may be redistributed to others.

In the example implementations described herein, the performance monitoring report generator apparatus 200 uses the commercial detection information 104 (FIGS. 1 and 2) to associate the detection of commercials with an audience measurement and a specific buy and to report the associated information. The performance monitoring report generator apparatus 200 enables users to submit a particular audience demographic and a ratings value expected to be achieved for a time period associated with a particular commercial along with buy information. For example, for each line of a spot-based and/or national-based buy (e.g., each ordered airing of a commercial), there may be one or more demographic/rating pairs. In the example implementations described herein, up to four demographic/rating pairs may be used. The four demographic types are referred to as the primary, secondary, tertiary, and quaternary demographics. In the example implementations described herein, for a spot-based buy, a user must provide a household ratings estimate as well. In the illustrated examples described herein, the performance monitoring report generator apparatus 200 matches each commercial detection to a single buy. Thus, the performance monitoring report generator apparatus 200 does not generally associate a commercial detection with a product, but instead with a buy so that the performance of the commercial detection can be determined and quantified based on the buy information.

FIG. 3 is a flow diagram representative of machine readable instructions that may be executed to implement the performance monitoring report generator apparatus 200 of FIG. 2. Some or all of the blocks of each the flow diagram may be representative of machine readable instructions that may comprise one or more programs for execution by one or more processors (e.g., the processor 2812 of FIG. 28), one or more controllers, and/or any other suitable devices. The one or more programs may be embodied in software stored on a tangible medium such as, for example, one or both of the memories 2824 and 2825 of FIG. 28. The entire program or programs and/or portions thereof could alternatively be executed by a device other than the processor 2812 and/or may be embodied in firmware or dedicated hardware in any desired manner (e.g., implemented using an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable logic device (FPLD), discrete logic, etc.). Also, some or all of the operations of the flow diagram of FIG. 3 may be implemented manually. Further, although the example method is described with reference to the flow diagram illustrated in FIG. 3, many other techniques for implementing the example methods and apparatus described herein may alternatively be used. For example, with reference to the flow diagram illustrated in FIG. 3, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, combined and/or subdivided into multiple blocks.

In the illustrated example of FIG. 3, the performance monitoring report generator apparatus 200 receives a detection record 301 (block 302) from the performance verifier apparatus 100 of FIG. 1. The detection record 301 is generated by the performance verifier apparatus 100 and includes information indicating that buys were matched with commercial detections to verify whether or not the buys were fulfilled. The information in the detection record is organized using the following headers: 1) time, 2) date, 3) station, 4) market, 5) buy (if matched to a buy), and 6) allowance status (before, during, or after an ordered time or time range).

If the example implementation includes both local and national commercial monitoring, the system may determine which type of commercial is associated with the detection record at this time. Using the detection record, the performance monitoring report generator apparatus 200 determines buy information (block 304). For example, if the detection record 301 indicates that a corresponding detected commercial is unmatched to a specific buy (e.g., it may have been generally matched to a product by the performance verification apparatus 100 of FIG. 1), the performance monitoring report generator apparatus 200 associates the unordered detection to a single buy. To match the commercial detection of the detection record 301 to a specific buy, the performance monitoring report generator apparatus 200 1) identifies all buys to which the detected commercial is trafficked; 2) identifies which buys include the detection record's market; 3) if only one buy includes the detection record's market, then assign the detection record 301 to that buy; 4) if more than one buy matches the market of the detection record, then identify which buys include the market and station for the detection record 301; 5) if only one buy includes the market and station of the detection record, then assign the detection record 301 to that buy; 6) if more than one buy matches the detection record's market and station, then identify which buys include the market, station and included dates w/in two weeks of for the detection; 7) if only one buy includes the detection record's market, station, and included dates, then assign the detection record 301 to that buy; 8) if more than one buy matches the detection record's market, station, and included dates, then identify which buys include the market, station, and week-of for the detection record 301; 9) if only one buy matches the detection record's market, station, and week-of, then assign the detection record 301 to that buy; 10) if more than one buy matches the detection record's market, station, and week-of, determine which buy has the earliest start date; 11) if only one buy has the earliest start date, then assign the detection record 301 to that buy; 12) if more than one buy share the same earliest start date, then determine which buy has the lowest estimate number; and 13) assign the detection record 301 to the buy with the lowest estimate number.

The estimate or campaign for the buy determined at block 304 is then set (block 306) based on the buy information and any other user-submitted information. The performance monitoring report generator apparatus 200 then converts the detection time of the detection record into quarter hour segments (block 308). For example, a detection time of (09:12:56) is converted to a quarter hour (09:00-09:14:59). Users are allowed to configure a permitted allowance for matching detections to buys. For example, with a 2 minute allowance, the system will match a 4:58:36 detection to a 5:00-7:00 buy. When an allowance match is made, the detection quarter hour is set as the nearest quarter hour within the buy instructions. Each matched detection record reports a character (e.g., B, D or A) to indicate if the detection was [B]efore the buy, but in the allowance, [D]uring the buy, or [A]fter the buy, but in the allowance. The character is used to determine the closest quarter hour within the buy.

The performance monitoring report generator apparatus 200 then selects a ratings source (block 310). For example, the performance monitoring report generator apparatus 200 of the illustrated example loads Nielsen Audience Measurement data into a database as those measurements are made available to the public. There are different sources for different markets and market coverage. To select a source, the performance monitoring report generator apparatus 200 of the illustrated example evaluates how a user configured the buy and the ratings sources available to determine which is the best ratings source to use. For example, if the Viewers In Profile (VIP) report from Nielsen Media Research is available for a detection market and date, it is used. If it is not available, the Nielsen Media Research Live+7 report is used. If the Live+7 report is not available, the Nielsen Media Research Overnight report is used. If none of the reports are available, a ratings source may not be set and modeling rules may be used (as described in further detail below). Additionally, a user may specify that modeling rules should be used even when a report is available.

The performance monitoring report generator apparatus 200 then matches the detection to measurements (block 312). Using the quarter hour and date of the detection and the rating source previously selected, the system retrieves the appropriate impressions and universal estimate. A television rating is calculated using ratings formulas (e.g., ratings formulas published by Nielsen Media Research). If no rating source was selected, this block may be skipped.

After matching detections to measurements (block 312), the ratings information is validated (block 314). For example, the ratings information must have sufficient in-tab and must be statistically significant. Then, the performance monitoring report generator apparatus 200 of the illustrated example applies special buy rules and changes ratings values as specified by the rules (block 316). For example, if a buy includes a “-s” value in a line of the buy, the system is instructed to use the target ratings value in place of the actual ratings value in its reports (Dash S feature). In another example, if a buy is for an exact time either on the hour or half hour, the system is instructed to average the two adjacent quarter hours and use that average in place of the actual ratings value (Break-buy feature).

Then, the performance monitoring report generator apparatus 200 applies modeling rules (block 318). In the illustrated example, modeling is the estimation of a television rating when no true rating is available. For example, in a first market, no overnight demographic ratings are available and in another market no VIP ratings are released. When no ratings information is available, model ratings are used. For example, model demographics may be estimated based on households and/or all values of information may be estimated. For example, when demographic ratings are not available for a market, a modeling demographic is calculable by taking the ratio between the estimated household rating provided in the buy and the actual household rating and, then, applying it to the estimated demographic rating to achieve a modeled demographic rating. In another example, when no ratings source is available for several months, targeted ratings values from the buy may be used as the actual values.

Then, the performance monitoring report generator apparatus 200 stores the detection record and corresponding ratings information to a database (block 320). The detection record and/or ratings information can be retrieved from the database to analyze the results of a campaign.

FIGS. 4-24 are graphical user interfaces that allow users to access and use the example performance monitoring report generator apparatus of FIG. 2. The example graphical user interfaces allow users to monitor whether the television commercial campaigns they have bought are aired as ordered and get the market weight and pressure desired by advertisers.

FIG. 4 is a user login user interface screen to authenticate registered users and grant those users access to the example performance monitoring report generator apparatus of FIG. 2. Access to the registered user homepage is restricted and is controlled by the log-on function from the default homepage. The screen contains four basic modules: marketing messages 402, system messages 404, a search function 406, and administration links 408. In the illustrated example, the search function 406 and the administrative links 408 are based on the user's user-type. In the illustrated example, an agency administration link 410 links to a system administrator user interface (e.g., the system administrator user interface screen of FIG. 6). A campaign administration link 412 links to an advertisement campaign user interface (e.g., the advertisement campaign user interface screen of FIG. 9). A traffic administration link 414 links to a traffic user interface screen (e.g., the traffic user interface screen of FIG. 13).

FIG. 5 is a search user interface screen to enable users to request reports from the example performance monitoring report generator apparatus of FIG. 2. The search function is a form in which the user selects information from pull-downs, pop-up calendars, and radio buttons. The data grid of the search results is based on the search criteria entered and the user's permissions.

FIG. 6 is a system administrator user interface screen to enable administrator-level users to create advertising agency accounts. Within the system administrator user interface screen the user creates agency accounts, adds advertiser and product records to those accounts, and then creates the initial user accounts for the agency. The system administrator user interface screen of the illustrated example includes tabs that allow a user to select which type of record to input. The print function causes a comma separated values (CSV) file to be downloaded containing the current data grid information.

FIG. 7 is a user records user interface screen to display registered users associated with different advertisement agencies. The example user records user interface screen of FIG. 7 is displayed when a user selects an advertiser/products tab of the system administrator user interface screen of FIG. 6. The print function causes a CSV file to be downloaded containing the current data grid information.

FIG. 8 is an advertiser/product records user interface screen to show advertiser and product information for different advertisement agencies. The example user records user interface screen of FIG. 8 is displayed when a user selects a users tab of the system administrator user interface screen of FIG. 6. The agency drop down menu allows users to select which agency's users are displayed. As items are selected from the drop down menu, the data grid changes. The print function causes a CSV file to be downloaded containing the current data grid information.

FIG. 9 is an advertisement campaign user interface screen to list advertising campaigns from different advertisers. When a user selects a campaign and chooses an enter new campaign button, the user is taken to a campaign/estimate screen (e.g., the campaign/estimate screen of FIG. 10) where the user can input new campaign information. In the illustrated example, when a user clicks on a number in an estimate column, the user is taken to a campaign/estimate screen that is pre-populated with information from the selected campaign so that the user can edit the information.

FIG. 10 is an entry/edit user interface screen to enable a user to enter estimated information related to commercial airings of an advertisement campaign. When a user is creating a new campaign, the entry/edit user interface screen is blank when a user reaches the screen. When a user is editing a campaign, the entry/edit user interface screen is pre-populated with information about the campaign to be edited. The entry/edit user interface screen includes several tabs. A list tab returns the user to the campaign list screen. A ratings methodology tab takes the user to a ratings methodology screen (e.g., the ratings methodology user interface screen of FIG. 11) where the user selects the ratings methodology for the display campaign. An implementation guidelines tab takes the user to an implementations guidelines screen (e.g., the implementation guidelines user interface screen of FIG. 12) where the user sets the implementation guidelines for the displayed campaign.

FIG. 11 is a ratings methodology user interface screen to enable a user to specify a particular ratings methodology to use for rating a particular advertisement campaign. The ratings methodology user interface screen includes a user election radio button for each type of metered market that allows a user to select whether modeled data should be used. The example ratings methodology user interface screen also includes a radio button to allow a user to select whether to model data in unmetered markets (e.g., where only VIP information is available). A user field and an approval date field enable a user to input identification information about who changed/set the values and the date on which the change/setting was made. A save button allows a user to save the data to the database.

FIG. 12 is an implementation guidelines user interface screen to enable a user to specify rules for how commercials are to be broadcast. A copy guidelines from another campaign drop down menu allows a user to select a previously existing campaign to populate the fields of the form.

FIG. 13 is an add/edit traffic user interface screen to enable a user to add or edit commercials for different advertisement campaigns. A user (e.g., an administrator) assigns commercials to campaigns. Commercials are referenced by an industry standard commercial identifier (ISCI). For example, each commercial has a unique ISCI. In the illustrated example, traffic is entered at the campaign level. The approved ISCI field contains ISCIs for traffic that exists for the campaign and allows a user to enter approved ISCIs for the campaign.

FIG. 14 is a multi-market view total user interface screen to enable a user to view total advertisement campaign performance information. Users arrive at the multi-market view total user interface screen when a search is executed on the authenticated user homepage. The data grid of the multi-market view are based on the search criteria. Each row of the data grid of the illustrated example is for a unique combination of advertiser, product, market, and estimate. A user can execute a new search by changing the form values and then selecting a fetch data button. A user can select one of a primary or secondary demographic associated with a campaign by selecting a radio button next to a desired demographic and selecting the fetch data button.

In the illustrated example, each campaign has an index that is calculated by dividing achieved gross rating points (GRPs) into the buy GRPs. A less-than display instructs the system to display only those campaigns that are performing below the numeric threshold set by the user. A less-than red index instructs the system to highlight in red the cells of the campaigns performing below the numeric threshold set by the user. For example, in the illustrated example, the index for Hewlett Packard is highlighted in red.

FIG. 15 is a multi-market view daypart user interface screen to enable a user to view daypart advertisement campaign performance information. The multi-market view daypart user interface screen displays how a single estimate has performed across many markets by daypart. In the illustrated example, each campaign has a primary and a secondary demographic assigned to it during set-up. The selection of a demographic affects the information presented in the example multi-market view daypart user interface screen. In the illustrated example, the Total value for each record is a hyperlink to a multi-market view total screen (e.g., the multi-market view total screen of FIG. 17). In the illustrated example, the Weekly value for each record is a hyperlink to a multi-market view weekly screen (e.g., the multi-market view weekly screen of FIG. 16).

FIG. 16 is a multi-market view weekly user interface screen to enable a user to view weekly advertisement campaign performance information. The multi-market view weekly user interface screen of the illustrated example displays how an estimate has performed across many markets by week.

FIG. 17 is a single-market performance user interface screen to display performance information of a single estimate in a single market. The single-market performance user interface screen shows the user the performance of a single estimate in a single market. An example implementation audit hyperlink causes the user to navigate to a guidelines violation report screen (e.g., the guidelines violation report screen of FIG. 23). An example station call letter hyperlink causes the user to navigate to a station view total screen (e.g., the station view total screen of FIG. 19) where the data is narrowed to a selected station. An example GRP index hyperlink causes the user to navigate to the station view total screen.

FIG. 18 is a single-market weekly performance user interface screen to display performance information of a single estimate in a single market by week. A day of the week data grid is populated based on a day of the week delivery drop down menu. For example, the drop down menu has a default value of cumulative, which indicates that an aggregation of values for all weeks in the campaign (limited by the search request) should be shown. The example drop down menu includes values for the completed weeks for the campaign. Selecting a weekly value from the drop down menu causes the day of the week data grid to display information for the selected week.

FIG. 19 is a station view total user interface screen to display total estimated versus actual rating and GRP data for a particular station. In the illustrated example, the station view total user interface screen is populated based on the last search conducted by a user.

FIG. 20 is a station view weekly user interface screen to display estimated versus actual rating and GRP data for a particular station by week. In the illustrated example, the station view weekly user interface screen is populated based on the last search conducted by a user.

FIG. 21 is a station view spot detail user interface screen to display detailed information about detected and bought spots for a particular station. In the illustrated example, the station view spot detail user interface screen displays a line-by-line detail of detected spots and bought spots including details of the buy, details of the airing of the spot, and ratings information about the airing compared with the estimated ratings information. The example station view spot detail user interface screen includes a missed units only function that allows a user to request that only information for spots that were bought but not detected be displayed. The station view spot detail user interface screen of the illustrated example includes a flash report function that allows the user to select rows from the data grid and send information from those rows to others via email or any other communication medium. A user can select one or more rows to be sent in a flash report. When a row is selected, the row is highlighted in yellow. When a row is selected a second time, the row is de-selected. After selecting a row, the user selects a flash report button, which causes a flash report user interface to be displayed (e.g., the flash report user interface screen of FIG. 22).

FIG. 22 is a flash report user interface screen to enable a user to select rows of data from different reports and send the data to a recipient party. For example, the flash report user interface enables a user to select rows of data from a multi-row data grid of one or more of the user interfaces described herein and send those rows of data along with comments to others via email. The flash report user interface of the illustrated example verifies that the email address input by the user is properly formed (e.g., includes an account, the @ symbol, and a domain name).

FIG. 23 is a guidelines violation report default user interface screen to display an overview of violation information associated with aired commercials. Users can reach the guidelines violation report default user interface screen by selecting a value displayed in an implementation audit column of a multi-market view total user interface (e.g., the multi-market view total user interface screen of FIG. 14) or by selecting an implementation audit button on a user interface (e.g., the implementation audit button on the station view weekly user interface screen of FIG. 20). In the illustrated example, when a user selects a station violation detail hyperlink the user is taken to a station violation detail screen (e.g., the station violation detail screen of FIG. 24). The guidelines violation report default user interface screen may include a link to return the user to the user interface screen from which the user linked to the guidelines violation report default user interface screen.

FIG. 24 is a station violation detail user interface screen to display detailed violation information associated with aired commercials. The station violation detail user interface screen may include a link to return the user to the user interface screen from which the user linked to the guidelines violation report default user interface screen.

FIG. 25 is an implementation guidelines user interface screen to allow a user to configure the detection of violations of the guidelines specified in a buy. Guideline verification allows a user (e.g., a buyer) to discern mid-buy whether a commercial occurrence should be considered part of the buy's fulfillment. Implementation guidelines of the illustrated example are rules concerning how commercials are to be aired. In the illustrated example, broadcasters are contractually obligated to follow guidelines specified in the buy. The guidelines input by the user in the implementation guidelines user interface screen are compared to the results of detections to determine if the airing of commercials complies with the guidelines.

For example, a guideline violation may occur when the wrong creative is detected for a commercial. In the illustrated example, the rating points associated with the wrong creative are tracked. The number of points required to meet the requirements of the buy are tracked.

Additionally, an example guideline violation occurs when a commercial is shown during excluded programming. For example, an advertiser may request that a commercial not be shown during a program that does not match the advertiser's desired demographic. In the illustrated example, users input the titles for programs that should be excluded. If the program during which the commercial was aired is on an excluded programs list, a guideline violation is reported.

Additionally, an example guideline violation occurs when a commercial is shown on the wrong day of the week.

Additionally, an example guideline violation occurs when commercials are not separated by a desired amount of time. In the illustrated example, a detection date and time for a commercial is compared with other detections for the same campaign to determine if a sufficient amount of time has passed. According to an example implementation, where a sufficient amount of time has not passed, ratings for the second occurrence are used for index calculation.

Additionally, an example guideline violation occurs when the maximum number of airings during a program has been reached for a commercial. For example, once a detection is matched to a campaign, the date, time, and program name are compared to previous detections to determine if a maximum number of spots designated in the buy has been reached.

FIG. 26 is an example multi-market view user interface screen that includes an audit index. The audit index identifies the percentage of reported GRPs that are attributed to commercials that violated implementation guidelines (e.g., the implementation guides specified in the implementation guidelines user interface screen of FIG. 25). The audit index value of the illustrated example is a hyperlink to a detail violations report (e.g., the violations report user interface screen of FIG. 27).

FIG. 27 is a violations report user interface screen that displays detailed information about guideline violations. In the illustrated example, every violation for a campaign is displayed under an applicable heading. According to the illustrated example, the complete detection record is displayed and violation elements are highlighted in red and ratings for the violating detection are highlighted in yellow.

FIG. 28 is a block diagram of an example processor system 2810 that may be used to implement the apparatus and methods described herein. As shown in FIG. 28, the processor system 2810 includes a processor 2812 that is coupled to an interconnection bus 2814. The processor 2812 may be any suitable processor, processing unit or microprocessor. Although not shown in FIG. 28, the system 2810 may be a multi-processor system and, thus, may include one or more additional processors that are identical or similar to the processor 2812 and that are communicatively coupled to the interconnection bus 2814.

The processor 2812 of FIG. 28 is coupled to a chipset 2818, which includes a memory controller 2820 and an input/output (I/O) controller 2822. As is well known, a chipset typically provides I/O and memory management functions as well as a plurality of general purpose and/or special purpose registers, timers, etc. that are accessible or used by one or more processors coupled to the chipset 2818. The memory controller 2820 performs functions that enable the processor 2812 (or processors if there are multiple processors) to access a system memory 2824 and a mass storage memory 2825.

The system memory 2824 may include any desired type of volatile and/or non-volatile memory such as, for example, static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, read-only memory (ROM), etc. The mass storage memory 2825 may include any desired type of mass storage device including hard disk drives, optical drives, tape storage devices, etc.

The I/O controller 2822 performs functions that enable the processor 2812 to communicate with peripheral input/output (I/O) devices 2826 and 2828 and a network interface 2830 via an I/O bus 2832. The I/O devices 2826 and 2828 may be any desired type of I/O device such as, for example, a keyboard, a video display or monitor, a mouse, etc. The network interface 2830 may be, for example, an Ethernet device, an asynchronous transfer mode (ATM) device, an 802.11 device, a DSL modem, a cable modem, a cellular modem, etc. that enables the processor system 2810 to communicate with another processor system.

While the memory controller 2820 and the I/O controller 2822 are depicted in FIG. 28 as separate functional blocks within the chipset 2818, the functions performed by these blocks may be integrated within a single semiconductor circuit or may be implemented using two or more separate integrated circuits.

FIGS. 25-28 illustrate example implementations of report user interfaces for displaying information related to maximum exposure for aired commercials. According to an example implementation, advertisers can request reports when a particular demographic exceeds a maximum threshold for percentage of viewing audience. For example, advertisers of pharmaceuticals, adult beverages, tobacco products, need to ensure that they are not advertising products to minors. Accordingly, an advertiser can request a watch to be placed on a particular demographic group (e.g., children ages 2-17). Companies can use reports to show statutory compliance and voluntary self-regulation. Other companies can use these reports to ensure they are delivering not only to their target audience, but also are not delivering a message to an undesired demo. For example, a company may have a female targeted creative it does not want to air to large male audiences, fearing the female targeted commercial may diminish the product brand to male consumers. An example process that may be implemented by software, hardware, and/or any combination of software and hardware, may include:

1. The User enables a campaign to include a DemoWatch report.

2. The user sets the watch demo.

3. The system collects detections of commercials for the campaign.

4. The system associates the detections with viewer impressions for both total viewers and the watch demo.

5. The system divides watch demo impressions by total viewer impressions to determine the percentage of watch demo that view the commercial occurrence.

6. If the demo watch viewership exceeds the threshold, the system records the occurrence as a demo watch violation.

7. The system reports all DemoWatch violations in online and digital download formats.

Although certain methods, apparatus, systems, and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. To the contrary, this patent covers all methods, apparatus, systems, and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents. 

What is claimed is:
 1. A method for monitoring the airing of advertisement, the method comprising: receiving an identification of an advertisement that was presented on a media presentation channel at a time; receiving ratings information for the media presentation channel associated with the time period; identifying a buy order for the received identification; receiving a purchased ratings value associated with the buy order; comparing the purchased ratings value to the ratings information; and displaying an indication of whether the ratings information is less than the purchased ratings value. 